Purchase order list

ABSTRACT

A method and system for organizing purchasing data for a plurality of items is disclosed. The method includes receiving purchasing data for the plurality of items, and generating a purchase order list from the purchasing data. The purchase order list comprises a list of the plurality of items and purchasing data for each item. The system includes means for receiving purchasing data for the plurality of items, and means for generating a purchase order list from the purchasing data, wherein the purchase order list comprises a list of the plurality of items and purchasing data for each item.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 60/551,221, filed Mar. 8, 2004 and entitled “Inventory Management,” and U.S. Provisional Application No. 60/563,284, filed Apr. 16, 2004 and entitled “Inventory Management,” both of which are hereby incorporated by reference.

BACKGROUND

The present description relates generally to the field of managing purchase orders. More particularly, the present description relates to the creation of line items for a purchase order list in a purchase order system.

Providers of retail sales articles and services must seek to provide the right product, at the right place, at the right time. Particularly, with regard to sales of retail fashion articles, these articles often have a short life cycle, and new articles have to be presented quite frequently. At the same time, the consumers demand a wide assortment variety. Accordingly, large numbers of different fashion articles often have to be processed and procured within extremely short time frames.

Further, tracking inventory and budgets for seasonal items can be important to the profitability of a business. For example, identifying a particularly fast selling item and ordering additional quantities to arrive on time and within a prescribed budget may increase the profitability of a retail location. Accordingly, it is important for a business to carefully plan and schedule purchasing orders for retail sales articles and services to ensure on-time procurement or scheduling within budget constraints. Optimizing the smooth flow of the procurement process increases an enterprise's efficiency and competitiveness and determines its success.

In view of the foregoing, it would be beneficial to provide a purchase order list for organizing purchasing data for sales articles and services to be purchased. It would further be beneficial to provide a purchase order list which may be sorted according to a particular type of purchasing data related to the sales articles or services in the list. It would be further beneficial to provide a purchase order list which may be updated to include data related to a specific purchase order generated for a particular retail sales article or service.

SUMMARY

According to an exemplary embodiment, a method of organizing purchasing data for a plurality of items includes receiving purchasing data for the plurality of items, and generating a purchase order list from the purchasing data, wherein the purchase order list comprises a list of the plurality of items and purchasing data for each item.

According to another exemplary embodiment, a system for organizing purchasing data for a plurality of items includes means for receiving purchasing data for the plurality of items. The system also includes means for generating a purchase order list from the purchasing data, wherein the purchase order list comprises a list of the plurality of items and purchasing data for each item.

According to another exemplary embodiment, a program product for organizing purchasing data for a plurality of items includes machine-readable program code for causing, when executed, one or more machines to perform the following method steps: receiving purchasing data for the plurality of items, and generating a purchase order list from the purchasing data, wherein the purchase order list comprises a list of the plurality of items and purchasing data for each item.

Other features and advantages of the present invention will become apparent from the following detailed description and accompanying drawings. It should be understood, however, that the detailed description and specific examples are given by way of illustration and not limitation. Many modifications and changes within the scope of the present invention may be made without departing from the spirit thereof, and the invention includes all such modifications.

BRIEF DESCRIPTION OF THE DRAWINGS

The exemplary embodiments will hereafter be described with reference to the accompanying drawings, wherein like numerals depict like elements, and:

FIG. 1 is a data flow diagram illustrating a system for facilitating planning and procurement of retail sales articles and services according to an exemplary embodiment;

FIG. 2 illustrates a graphical user interface screen for selecting grouping criteria according to an exemplary embodiment;

FIG. 3 is a flow diagram illustrating a method of using a purchase order list to generate a purchase order according to an exemplary embodiment;

FIG. 4 is a flow diagram illustrating a method of associating a purchasing contract with an item to be purchased according to an exemplary embodiment.

FIG. 5 illustrates the structure of a purchase order list according to an exemplary embodiment;

FIG. 6 illustrates the structure of a selection screen and purchase order list according to an exemplary embodiment;

FIG. 7 illustrates the structure of a selection screen according to another exemplary embodiment.

FIG. 8 illustrates the structure of a purchase order list having status indicators according to an exemplary embodiment;

FIG. 9 illustrates status indicator configurations according to another exemplary embodiment; and

FIG. 10 illustrates the structure of a purchase order list having status indicators according to another exemplary embodiment.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the present invention. It will be evident to one skilled in the art, however, that the exemplary embodiments may be practiced without these specific details. In other instances, structures and device are shown in diagram form in order to facilitate description of the exemplary embodiments.

FIG. 1 illustrates a system 100 for facilitating planning and procurement of retail sales articles and services according to an exemplary embodiment. System 100 is illustrated as including a back end system 110 (identified as “BW/SEM”) and a front end system 120 (identified as “R/3”). In another embodiment, a single integrated system may be used in place of back end system 110 and front end system 120. System 100 may be implemented as a single system, a distributed system, or any combination thereof. System 100 may be implemented using a single computing system, a plurality of computing systems, software, hardware, or any other system or combination of systems to perform the functions described herein. System 100 may be used, for example, to generate and manage purchase orders for retail sales articles and services using a purchase order list. This may include the automated determination of a pre-existing supplier contract for a particular article or group of articles to be procured.

Back end system 110 is a data repository configured to receive, sort, process, and store retail sales data, as well as to facilitate planning, provide reporting, and provide other functions associated with managing sales data using one or more functions and/or components. For example, in the illustrated embodiment, back end system 110 includes a strategic planning function 112. Strategic planning function 112 may be used to facilitate an overall business financial plan which defines the retailer's financial goals (e.g., revenues, gross margins, etc.), planned expenses (e.g., inventory, marketing, etc.), and budgets. Accordingly, strategic planning function 112 may be used to generate a store plan 114, an “Open To Buy” (OTB) plan 116, a merchandise plan 117, a capacity plan 118, and an assortment plan 119. According to other exemplary embodiments, back end system 110 may include additional, fewer, and/or different functions.

Store plan 114 may be a plan in which revenues and costs are based on factors within a store hierarchy such as regional marketing, competition, demographic shifts and preferences, and events. OTB plan 116 is derived from merchandise plan 117 and may be a plan designed to maximize turnover potential and minimize capital investment and stockholding costs. OTB planning data may include, for example, an extrapolated amount of available budget for procuring a retail sales article. Merchandise plan 117 may define target purchasing, sales, margin, and inventory levels that are consistent with the overall business plan. Capacity plan 118 is derived from merchandise plan 117 and may be a plan which takes into account the available shelf and/or floor space in a particular store or group of stores in order to determine an optimal number of certain types of retail sales articles to be procured for the store or group of stores.

Assortment plan 119 is based on merchandise plan 117 (and optionally on capacity plan 118 for certain articles) and may be a plan which defines ranges of retail sales articles (e.g., colors and sizes) that may be assigned to a particular grouping of stores. Assortment plan 119 may form the basis for selecting, procuring, and allocating quantities of particular retail sales articles. For example, in the illustrated embodiment, assortment planning data from assortment plan 119 is provided to front-end system 120 in order to facilitate generation and management of purchase orders for the associated retail sales articles.

Front end system 120 is communicatively coupled to back end system 110 and is similarly configured to receive, sort, process, and store retail sales data, as well as to facilitate planning, provide reporting, and provide other functions associated with managing sales data using one or more functions and/or components and in conjunction with back end system 110. For example, in the illustrated embodiment, front end system 120 includes operational assortment planning system 130, order manager system 160, operational purchasing system 170, and OTB procurement system 180. According to other exemplary embodiments, front-end system 120 may include additional, fewer, and/or different functions.

Operational assortment planning system 130 is configured to receive strategic planning data, such as merchandise plan data 117, capacity plan data 118, and assortment planning data 119, from back end system 110, to facilitate refinement and/or addition of detail to the strategic planning data (e.g., specific retail sales articles and quantities to be procured for specific stores during specific periods), and to distribute the data to other downstream processes. In the illustrated embodiment, operational assortment planning system 130 includes a layout engine 140 and an operative assortment planning and control (APC) engine 150. Data from layout engine 140 is passed on to APC engine 150 where it is processed and distributed to downstream processes.

Layout engine 140 is configured to receive strategic planning data from back end system 110, such as capacity data 118 and assortment planning data 119, and to use this data to assign, for example, certain types of retail sales articles to specific locations or layouts according to the available capacity in a store or group of stores. For example, in the illustrated embodiment, layout engine 140 may be used to assign basic, repeat, or “stackable” retail sales articles to a particular layout according to available capacities. In other embodiments, layout engine 140 may be used in conjunction with other types of retail sales articles. Layout data, such as assignments 142 of specific retail sales articles to a particular layout is then passed on to APC engine 150.

APC engine 150 is configured to receive strategic planning data from back end system 110 via an inbound interface, and/or assigned article data 142 from layout engine 140, and to determine groupings and quantities of specific retail sales articles that are to be procured during a specific period and delivered to a specific store or group of stores. By way of example, the following strategic planning data may be “pushed” (or written) or “pulled” (or read) by APC engine 150:

(i) Key performance indicator “fixed initial stock-up” (on a quantity and value basis: purchase price, sales price) at various levels (e.g., article hierarchy node, season/season year, rollout, global assortments assigned to the hierarchy node) Fixed initial stock-up represents fixed quantities of new merchandise to be procured from a capacity standpoint.

(ii) Key performance indicator “variable initial stock-up” on a quantity and value basis at the same levels. Variable initial stock-up represents quantities of new merchandise to be procured from a sales standpoint (e.g., forecast sales).

(iii) Key performance indicator “putaway quantity” on a quantity and value basis at various levels (e.g., article hierarchy node, season/season year, rollout, distribution center). Putaway quantity represents quantities of an article that are not to be shipped directly to a store, but rather are to be shipped to a distribution center first.

(iv) The number of different generic articles (or single articles) per key performance indicator in the assortments (assortment breadth).

APC engine 150 uses the strategic planning data received from back end system 110 and/or assigned article data 142 received from layout engine 140 to generate output data including planned assortments/store groups that, upon release, are pushed to downstream processes. Output data from APC engine 150 may also include one or more purchasing lists 152 of various types. For example, in the illustrated embodiment, APC engine 150 uses strategic planning data received from back end system 110 to generate one or more purchasing lists 152 a for fashion retail sales articles, and uses assigned article data 142 from layout engine 140 to generate one or more purchasing lists 152 b for non-fashion retail sales articles such as basics or stackable merchandise.

Purchasing list 152 is a list of retail sales articles and corresponding planned purchasing quantities for selected planning levels (e.g., article hierarchy node/season, season year/rollout/assortment type) in APC engine 150. Each purchasing list 152 includes one or more purchasing list items, which represent the smallest possible unit in each purchasing list. A purchasing list item may include a generic article, variants of the generic article (e.g., color or size ranges), or single articles. A purchasing list item may also include planned quantities that are planned within a purchasing list for a specific store delivery date for the various global assortments and key performance indicators. By way of example, each purchasing list item may include the following information:

-   -   (i) Purchasing list item number or identifier. This number         allows communication between APC engine 150 and the various         operative applications;     -   (ii) Article number or identifier;     -   (iii) Characteristic 1 (e.g., “article number-characteristic         level”). A data retention level of this type allows APC engine         150 to save confirmed order quantities at the characteristic         level and facilitates confirmation as to whether the order         quantities for a certain characteristic value deviate from the         planned quantities;     -   (iii) Market buying number. This number allows tracking of         specific generic articles that may be moved from one purchasing         list to another;     -   (iv) Prices (e.g., purchase price and sales price);     -   (v) Currencies (e.g., local currency, vendor currency);     -   (vi) “Price fixed” indicator. This indicator ensures that price         determination is not performed for either the purchase or sales         price during order processing;     -   (vii) Total purchase order quantity for articles—planned and         actual quantities (for confirmations from the purchase order)         and article/characteristic value;     -   (viii) Vendor. Where a vendor is not maintained by APC engine         150, the vendor may be determined from the purchase order list,         as will be described below;     -   (ix) Supplying site (e.g., distribution center, location for         delivery);     -   (x) Dates (e.g., store delivery date, distribution center         delivery date, latest possible order date), planned and actual         dates;     -   (xi) Fields for confirmations (e.g., confirmations from         downstream processes); and     -   (xii) Status fields for the purchasing list item (e.g., status         information from downstream processes).

Order manager system 160 is configured to receive data from APC engine 150 in the form of released purchasing list items, and to generate a corresponding purchase order list 162. Items in purchase order list 162 for which a purchase order is to be generated are transferred to a grouped procurement document 164. In one embodiment, items in purchase order list 162 for which a purchase order is to be generated may be grouped together for transfer to grouped procurement document 164 according to selected criteria (e.g., by using a graphical user interface). Grouping criteria for creating and changing purchase orders may include grouping based on, for example, a delivery period, a delivery date, a contract, an OTB budget, a purchasing group, a plant or location, an item category, etc. An exemplary graphical user interface screen for selecting such grouping criteria is show in FIG. 2. According to an exemplary embodiment, these criteria may be modified or enhanced by a user of system 100.

Items may also be revised if necessary after transfer to a grouped procurement document 164. For example, in one embodiment, vendor determination function 191 and contract determination function 192 may be carried out for items in grouped procurement document 164 if these functions were not performed for purchase order list 162. Once an item has been transferred to the grouped procurement document 164, a confirmation is sent to APC engine 150 (e.g., as a status field for the corresponding purchasing list item) and the item is identified for removal from purchase order list 162 by setting a deletion indicator in the purchased list. Items identified for removal from purchase order list 162 remain, however, in purchasing list 152. Items transferred to grouped procurement document 164 may be returned to purchase order list 162 by removing the deletion indicator and sending another confirmation to to APC engine 150. All items in purchase order list 162 that remain marked for deletion are deleted upon generation of a purchase order 168 from grouped procurement document 164.

Once grouped order document 164 has been prepared, order manager 160 performs an OTB check 166 to verify that budgeted funds are available such that a purchase order may be generated. If OTB check 166 is successful, a confirmation may be sent to APC engine 150 (e.g., as a status field for the corresponding purchasing list item) and order manager system 160 may then generate a purchase order 168. If OTB check 166 is not successful, a failure message may be sent to APC engine 150 (e.g., as a status field for the corresponding purchasing list item). The grouped purchase order document may then need to be modified and/or specially authorized such that a purchase order may be generated.

Operational purchasing system 170 is configured to perform OTB check 166 in conjunction with order manager system 160. Operational purchasing system 170 includes planned OTB data 172 and actual OTB data 174. Planned OTB data may include OTB plan data 116 received by operational purchasing system 170 from back end system 110. Operational purchasing system 170 uses planned OTB data 172 and actual OTB data 174 to determine whether budgeted funds are available such that a purchase order may be generated for a particular grouped order document 164.

OTB procurement system 180 is in communication with order manager system 160 and operational purchasing system 170 and is configured to provide options for successfully generating a purchase order for grouped procurement document 164 when OTB check 166 is not successful. For example, in the illustrated embodiment, OTB procurement system 180 includes OTB dialog 182, which provides options to either initiate a special release 184 or a purchase order change 186. When special release 184 is initiated, grouped procurement document 164 is forwarded to, for example, an appropriately authorized individual for approval. When purchase order change 186 is initiated, grouped procurement document 164 may be modified. Such modifications may include changes in quantities, changes in delivery dates, changes in price, etc.

FIG. 3 illustrates a method of using a purchase order list to generate a purchase order according to an exemplary embodiment. The process begins with a step 310. In step 310, released purchasing list items are received and a purchase order list is generated which includes a corresponding line item for each released purchasing list item. In a step 320, particular items in the purchase order list for which a purchase order is to be generated are transferred to a grouped procurement document. In a step 330, an OTB check is performed on the grouped procurement document to verify that sufficient budget is available for a purchase order to be generated. If the OTB check is not successful, the process continues with a step 340. If the OTB check is successful, the process continues with a step 350. In step 340, the grouped procurement document may be subject to modification or special approval. For example, the grouped procurement document may be subject to approval via a special release as described above, or may be subject to modifications. In one embodiment, such modifications may include changes in quantities, changes in delivery dates, changes in price, etc. In step 350, a purchase order is generated for items in the grouped procurement document.

Referring again to FIG. 1, order manager system 160 may also be configured to determine a suitable source or vendor, including selecting a relevant existing purchasing contract, for an item in purchase order list 162 as mentioned above. For example, order manager system 160 may utilize a vendor determination function 191 in order to automatically determine a suitable vendor for an item in purchase order list 162, such as items in purchase order list 162 for which relevant vendor data was not transferred from APC engine 150. Vendor determination function 191 may include a specific procedure for uniquely identifying a particular vendor (which the user may optionally designate as a preferred vendor) for an item in purchasing list 162. According to an exemplary embodiment, if vendor determination function 191 is unable to identify a unique vendor for a particular item in purchase order list 162, the user is presented with a list from which a relevant vendor for the item may be selected manually.

Order manager system 160 may also utilize a contract determination function 192 in order to determine and assign a reference or link to a relevant existing purchasing contract with the identified vendor (e.g., a vendor identified based on vendor data from APC engine 150 or by vendor determination function 191) for an item in purchase order list 162. According to an exemplary embodiment, order manager system 160 may also be configured to use contract determination function 192 to determine and assign a reference or link to a relevant existing purchasing contract for ad-hoc items or other items in purchase order list 162 for which a vendor was manually specified by a user.

As with source determination function 191, contract determination function 192 may include specific procedures for identifying a unique contract for an item in purchase order list 162. For example, in one embodiment, contract determination function 192 may be configured to utilize the oldest existing contract where there are multiple existing purchasing contracts which may be relevant to a particular item in purchase order list 162. If contract determination function 192 is able to identify a unique purchasing contract, a reference associating the purchasing contract with the item in purchase order list 162 may be generated, and the purchase price specified in the contract may be transferred from the contract to the item in purchase order list 162. According to an exemplary embodiment, the purchase price or other data specified in the purchasing contract is used automatically unless the purchase price field in purchase order list 162 cannot be manually or otherwise edited as indicated to the user by, for example highlighting or gray shading as shown in FIG. 5. Where contract determination function 192 is unable to uniquely identify a unique purchasing contract for a particular item in purchase order list 162, a contract may be identified manually. According to an exemplary embodiment, for example, if contract determination function 192 is unable to identify a unique purchasing contract for a particular item in purchase order list 162, the user is presented with a list from which a relevant existing purchasing contract may be selected manually.

According to an exemplary embodiment, a user may activate or deactivate contract determination function 192 in order manager system 160 based on a customized setting in customizing engine 190. For example, in one embodiment, customizing engine 190 may include a purchase order handling setting which may be set to “ON” in order to activate contract determination function 192, and to “OFF” in order to deactivate contract determination function 192.

FIG. 4 illustrates a process of associating a purchasing contract with an item to be purchased according to an exemplary embodiment. The process begins with a step 405. In step 405 purchasing data is received for an item to be purchased. The purchasing data may be received from, for example, APC engine 150 (shown in FIG. 1), or from an ad-hoc item entry. In a step 410, if vendor data for the item to be purchased is included in the received purchasing data, the process continues with step a 430. If vendor data is not received, the process continues with a step 415.

In step 415, a vender associated with the item to be purchased is determined. According to an exemplary embodiment, the vender associated with the item to be purchased is automatically determined using vendor determination function 191 (shown in FIG. 1). In a step 420, if a unique vendor is determined, the process continues with step 430. If a unique vendor is not determined (e.g., multiple vendors exist or no vendor is identified), then the process continues with a step 425. In step 425, a vendor for the item to be purchased is determined manually. According to an exemplary embodiment, a vendor for the item to be purchased is determined manually by a user from a list of possible vendors for the item to be purchased. Once a vendor has been manually determined, the process continues with step 430.

In step 430, a purchasing contract is selected for the item to be purchased based on the received purchasing data. According to an exemplary embodiment, the purchasing contract associated with the item to be purchased is automatically selected using contract determination function 192 (shown in FIG. 1). In a step 435, if a unique purchasing contract is determined, the process continues with a step 445. If a unique purchasing contract is not determined (e.g., multiple purchasing contracts exist or no purchasing contract is identified), then the process continues with a step 440. In step 440, a purchasing contract for the item to be purchased is selected manually. According to an exemplary embodiment, a purchasing contract for the item to be purchased is selected manually by a user from a list of possible purchasing contracts for the item to be purchased. Once a vendor has been manually selected, the process continues with step 445.

In step 445, a reference associating the selected purchasing contract with the item to be purchased is generated. In a step 450, data from the selected purchasing contract may be associated with the item to be purchased. For example, according to an exemplary embodiment, the purchase price specified in the purchasing contract may be transferred from the purchasing contract to the item to be purchased in purchase order list 162 (shown in FIG. 1).

FIG. 5 illustrates the structure of a purchase order list 500 which may be displayed to a user as part of a graphical user interface according to an exemplary embodiment. In the illustrated embodiment, purchase order list 500 is formatted as a table. Purchase order list 500 includes a header row 501 as well as a row 502 for each purchasing list item added to the purchase order list. For example, in the illustrated embodiment, purchase order list 500 includes rows 502 a-502 n. Purchase order list 500 also includes columns 504 for relevant purchasing data associated with each purchasing list item in the purchase order list. For example, in the illustrated embodiment, purchase order list 500 includes columns 504 a-504 k. Column 504 a, labeled “No.” in header row 501, includes the purchase list number from which the purchase order list line item was generated. For example, the purchase order list line items in rows 502 a-502 e were all generated from purchasing list number 12345678. Column 504 b, labeled ‘Item” in header row 501, includes the purchasing list line item number for each purchasing list item in the purchase order list. For example, the purchase order list line items in rows 502 a-502 e represent line items 10-50 from purchasing list number 12345678. Column 504 c, labeled “Origin” in header row 501, includes the origin of each purchase order list line item. The origin may come from the purchase list, an external system, or may be input manually. Column 504 d, labeled “Article” in header row 501, includes the specific article number for each purchase order list line item. Column 504 e, labeled “Latest PO Date” in header row 501, lists the latest possible date that a purchase order may be generated for each purchase order list line item. Column 504 f, labeled “Vendor” in header row 501, lists the vendor for each purchase order list line item. Column 504 g, labeled “Delivery Date GR Ramp” in header row 501, includes the required delivery date for each purchase order list line item. Column 504 h, labeled “Price” in header row 501, includes the price for each purchase order list line item. Column 504 i, labeled “Quantity” in header row 501, includes the required quantity for each purchase order list line item. Column 504 j, labeled “UoM” in header row 501, includes the appropriate unit of measure for each purchase order list line item (e.g., cartons, pieces, etc.) Column 504 k, labeled “Site” in header row 501, lists the delivery destination for each purchase order list line item. Of course, in other embodiments, additional, fewer, and/or different columns and rows of information or data may be displayed.

Purchase order list line items may be selectively accessed and displayed. For example, FIG. 6 illustrates a purchase order list 600 and a selection screen 610 which may be displayed as part of the graphical user interface in order to facilitate the selective accessing of purchase order list line items according to specific criteria according to an exemplary embodiment. Such criteria may include categories of relevant purchasing data associated with each purchasing list item in purchase order list 600. In the illustrated embodiment, the categories “Latest PO Date,” “Article No.,” and “Site” may be used in selection screen 610 to selectively access purchase order list line items. For example, in the illustrated embodiment, where the Latest PO Date “23 Sep. 2002” and the Site “VZ01” are entered in selection screen 610, purchase order list 600 is displayed including only those purchase order list line items corresponding to site VZ01 with a latest PO date prior to or on 23 Sep. 2002.

FIG. 7 illustrates a selection screen according to another exemplary embodiment. In this embodiment, additional categories include “Purchasing Organization,” “Purchasing Group,” “Vendor,” “Material,” “Plant,” “Plant Category,” “Delivery Date,” “Firm Deal,” “Release Indicator,” and “Order Type.”

FIG. 8 illustrates the structure of a purchase order list 800 having status indicators 830 for each purchase order list line item according to an exemplary embodiment. In the illustrated embodiment, purchase order list 800 includes line items 802 a, 802 b, and 802 c, which correspond to items from entries 820 and 822 (shown for reference). When each item is entered, purchase order list 800 adds each item as a purchase order list line item with columns 804 a-804 k, which contain the relevant purchasing data associated with each ad-hoc item. Purchase order list 800 also includes column 804 m, which may contain an individual status identifier 830 for purchase order list line items 802 a, 802 b, and 802 c.

Status identifier 830 may be any of many possible configurations. In the illustrated embodiment, status identifier 830 consists of three circular areas, wherein each circular area is representative of a different status level, and the current status level is displayed by filling, highlighting, shading, or otherwise denoting the circular area corresponding to the current status (e.g., red, yellow, green colors of the circular areas). In another embodiment, status identifier 830 may include a different number of circular areas to indicate additional or fewer status levels. In yet another embodiment, status identifier 830 may include areas or icons of different shapes (e.g., square areas, triangular areas etc.) for indicating the current status. In yet another embodiment, status identifier 830 may include the use of different colors and/or changes in size or shape or other attributes of the appearance of a single area or icon, or of multiple areas or icons to indicate the current status (e.g., the use of an “X” or “check mark” or other character or symbol to modify the appearance of an area or icon). In yet another embodiment, status identifier 830 may include the use of alphanumeric text, such as a numeric scale (e.g., 1-10) to indicate the current status, wherein the number or other text indicates the current status. In yet another embodiment, a combination of area shapes, icons, colors, and/or alphanumeric text may be used to indicate a number of different possible status levels. Examples of other configurations of status indicators are shown in FIG. 9.

Referring again to FIG. 8, status identifier 830 may also indicate many different types of information. For example, in the illustrated embodiment, status indicator 830 may be used to indicate information as to whether a purchase order has been successfully generated for each line item in purchase order list 800. In this embodiment, a first one of the three circular areas may be used to indicate that a purchase order has been successfully generated for the particular line item, a second one of the three circular areas may be used to indicate that a purchase order has not yet been generated for the particular line item, and a third one of the three circular areas may be used to indicate that there is insufficient budget available to generate a purchase order (e.g., an unsuccessful OTB check). The appropriate circular area may then be filled, e.g., using one of the indication methods described above, to indicate the current status of each line item. For example, in one embodiment, a first one of the three circular areas may be displayed as filled with the color green to indicate that a purchase order has been successfully generated for the particular line item, a second one of the three circular areas may be displayed as filled with the color yellow to indicate that a purchase order has not yet been generated for the particular line item, and a third one of the three circular areas may be displayed as filled with the color red to indicate that there is insufficient budget available to generate a purchase order (e.g., an unsuccessful OTB check). In the illustrated embodiment, the middle circle has been filled to indicate that a purchase order has not yet been generated for each of the ad-hoc line items in purchase order list 800. According to various other embodiments, status identifier 800 may indicate other types of information, such as, for example, OTB information, date control information, allocation table information, firm deal information, release indicator information, etc.

FIG. 10 illustrates the structure of a purchase order list 1000 having status indicators 1030 according to another exemplary embodiment. In the illustrated embodiment, purchase order list 1000 includes a number of line items 1002 and columns 1004 a-1004 k, which contain the relevant purchasing data associated with each purchase order list line item. Purchase order list 1000 also includes column 1004 m, which may contain an individual status identifier 1030 for purchase order list line items 1020 to identify whether a purchase order has been successfully generated for each line item. For example, in the illustrated embodiment a first one of the three circular areas has been identified to indicate that a purchase order has been successfully generated for each line item 1002.

Purchase order list 1000 further includes columns 1004 n, 1004 p, and 1004 q. Column 1004 n is labeled “Order No.,” and includes the purchase order number of the successfully generated purchase order for each line item 1002 in purchase order list 1000. Column 1004 p is labeled “PO Item,” and includes the item number from a particular purchase order number for each line item 1002 in purchase order list 1000. Column 1004 q is labeled “Currency,” and denotes the type of currency (e.g., euro, dollar, etc.) used in each successfully generated purchase order.

The use of a purchase order list provides the advantage of organizing purchasing data for retail sales articles and/or services to be purchased such that the generation of purchase orders for these articles and/or services may be conveniently managed. Improved purchase order management and organization is achieved by providing for the sorting of sales articles or services in the purchase order list according to a particular type of purchasing data related to the sales articles or services in the list, such as required order and delivery dates. Improved purchase order management and organization is further achieved by providing for the updating of the purchase order list to include data related to a specific purchase order generated for a particular retail sales article or service. In this way, a business may carefully plan and schedule purchasing orders for retail sales articles and services to ensure on-time procurement or scheduling.

Embodiments within the scope of the present description include program products comprising computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, such computer-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above are also to be included within the scope of computer-readable media. Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.

The invention is described in the general context of a process, which may be implemented in one embodiment by a program product including computer-executable instructions, such as program code, executed by computers in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

The present invention in some embodiments, may be operated in a networked environment using logical connections to one or more remote computers having processors. Logical connections may include a local area network (LAN) and a wide area network (WAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets and the Internet. Those skilled in the art will appreciate that such network computing environments will typically encompass many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

An exemplary system for implementing the overall system or portions of the invention might include a general purpose computing device in the form of a conventional computer, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The system memory may include read only memory (ROM) and random access memory (RAM). The computer may also include a magnetic hard disk drive for reading from and writing to a magnetic hard disk, a magnetic disk drive for reading from or writing to a removable magnetic disk, and an optical disk drive for reading from or writing to removable optical disk such as a CD-ROM or other optical media. The drives and their associated computer-readable media provide nonvolatile storage of computer-executable instructions, data structures, program modules and other data for the computer.

Software and web implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps. It should also be noted that the word “component” as used herein and in the claims is intended to encompass implementations using one or more lines of software code, and/or hardware implementations, and/or equipment for receiving manual inputs.

The foregoing description of embodiments of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. The embodiments were chosen and described in order to explain the principals of the invention and its practical application to enable one skilled in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. 

1. A method of organizing purchasing data for a plurality of items, the method comprising: receiving purchasing data for the plurality of items; and generating a purchase order list from the purchasing data, wherein the purchase order list comprises a list of the plurality of items and purchasing data for each item.
 2. The method of claim 1, wherein the purchasing data includes at least one of an item identifier, a quantity, a price, an order date, a delivery date, and a delivery location.
 3. The method of claim 1, wherein the purchase order list is configured to be sorted according to different types of purchasing data.
 4. The method of claim 3, wherein the purchase order list is configured to be sorted using a graphical user interface.
 5. The method of claim 1, further comprising updating the purchase order list to include data from a purchase order that has been generated for an item in the purchase order list.
 6. The method of claim 1, wherein the purchasing data includes data manually entered by a user.
 7. The method of claim 1, wherein the items include at least one of a retail sales article and a service.
 8. The method of claim 1, wherein the purchasing data includes data received from a purchasing list.
 9. The method of claim 8, wherein the purchasing list is a list of retail sales articles and corresponding planned purchasing quantities for selected planning levels.
 10. A system for organizing purchasing data for a plurality of items, the system comprising: means for receiving purchasing data for the plurality of items; and means for generating a purchase order list from the purchasing data, wherein the purchase order list comprises a list of the plurality of items and purchasing data for each item.
 11. The system of claim 10, wherein the purchasing data includes at least one of an item identifier, a quantity, a price, an order date, a delivery date, and a delivery location.
 12. The system of claim 10, wherein the purchase order list is configured to be sorted according to different types of purchasing data.
 13. The system of claim 12, wherein the purchase order list is configured to be sorted using a graphical user interface.
 14. The system of claim 10, further comprising means for updating the purchase order list to include data from a purchase order that has been generated for an item in the purchase order list.
 15. The system of claim 10, wherein the purchasing data includes data manually entered by a user.
 16. The system of claim 10, wherein the items include at least one of a retail sales article and a service.
 17. The system of claim 10, wherein the purchasing data includes data received from a purchasing list.
 18. The system of claim 17, wherein the purchasing list is a list of retail sales articles and corresponding planned purchasing quantities for selected planning levels.
 19. A program product for organizing purchasing data for a plurality of items, the program product comprising machine-readable program code for causing, when executed, one or more machines to perform the following method steps: receiving purchasing data for the plurality of items; and generating a purchase order list from the purchasing data, wherein the purchase order list comprises a list of the plurality of items and purchasing data for each item.
 20. The program product of claim 19, wherein the purchasing data includes at least one of an item identifier, a quantity, a price, an order date, a delivery date, and a delivery location.
 21. The program product of claim 19, wherein the purchase order list is configured to be sorted according to different types of purchasing data.
 22. The program product of claim 21, wherein the purchase order list is configured to be sorted using a graphical user interface.
 23. The program product of claim 19, wherein the machine-readable program code is further configured to cause, when executed, one or more machines to perform the method step of updating the purchase order list to include data from a purchase order that has been generated for an item in the purchase order list.
 24. The program product of claim 19, wherein the purchasing data includes data manually entered by a user.
 25. The program product of claim 19, wherein the items include at least one of a retail sales article and a service.
 26. The program product of claim 19, wherein the purchasing data includes data received from a purchasing list.
 27. The program product of claim 26, wherein the purchasing list is a list of retail sales articles and corresponding planned purchasing quantities for selected planning levels. 